Fix CargoKit plugin detection for current Flutter Android builds - #246
Draft
Xare123 wants to merge 4 commits into
Draft
Fix CargoKit plugin detection for current Flutter Android builds#246Xare123 wants to merge 4 commits into
Xare123 wants to merge 4 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
CargoKit can silently skip or hang native plugin builds when Flutter plugin class names and target-platform properties differ from older assumptions. A green APK may then omit required Rust native libraries.
Change
Handle direct Flutter project/plugin detection safely, propagate target platform consistently, patch affected pub-cache CargoKit copies idempotently, and assert every required native library exists in the APK.
Validation
git diff --checkand scope checks passScope and sequencing
No sampler, Windows, signing, or Cloud Sync behavior. This branch is independently based on
rustpush; CI execution is expected to provide the full APK proof and it can land after the CI modernization draft.